DNSWHOIS.INFO - saml.to

Search for IP or hostnames:

saml.to checked at 2025-09-06T08:57:14.118Z 265ms 153/153/153 100% R:16

`saml.to`

NS	`ns-269.awsdns-33.com`
		A	2600:9000:5301:d00::1 ^{🇺🇸 Amazon}
			PTR	`ns-269.awsdns-33.com`
		A	205.251.193.13^{🇺🇸 Amazon}
			PTR	`ns-269.awsdns-33.com`
NS	`ns-906.awsdns-49.net`
		A	2600:9000:5303:8a00::1 ^{🇺🇸 Amazon}
			PTR	`ns-906.awsdns-49.net`
		A	205.251.195.138^{🇺🇸 Amazon}
			PTR	`ns-906.awsdns-49.net`
NS	`ns-1291.awsdns-33.org`
		A	2600:9000:5305:b00::1 ^{🇺🇸 Amazon}
			PTR	`ns-1291.awsdns-33.org`
		A	205.251.197.11^{🇺🇸 Amazon}
			PTR	`ns-1291.awsdns-33.org`
MX	`aspmx.l.google.com`
		A	2607:f8b0:4004:c19::1b ^{🇺🇸 Google}
			PTR	`bk-in-f27.1e100.net`
		A	142.251.111.26^{🇺🇸 Google}
			PTR	`bk-in-f26.1e100.net`
NS	`ns-1913.awsdns-47.co.uk`
		A	2600:9000:5307:7900::1 ^{🇺🇸 Amazon}
			PTR	`ns-1913.awsdns-47.co.uk`
		A	205.251.199.121^{🇺🇸 Amazon}
			PTR	`ns-1913.awsdns-47.co.uk`
MX	`alt1.aspmx.l.google.com`
		A	2a00:1450:400b:c02::1b ^{🇮🇪 Google}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google}
			PTR	`dj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`
		A	2a00:1450:400c:c00::1a ^{🇧🇪 Google}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.26^{🇺🇸 Google}
			PTR	`ws-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`
		A	2a00:1450:4025:402::1a ^{🇳🇱 Google}
			PTR	`rb-in-f26.1e100.net`
		A	142.250.102.26^{🇺🇸 Google}
			PTR	`rb-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`
		A	2a00:1450:4013:c1c::1b ^{🇳🇱 Google}
			PTR	`yugrqog-in-f27.1e100.net`
		A	192.178.156.27^{🇺🇸 Google}
			PTR	`yugrqog-in-f27.1e100.net`
A	18.165.83.92^{🇺🇸 Amazon}
		PTR	`server-18-165-83-92.iad55.r.cloudfront.net`
A	18.165.83.110^{🇺🇸 Amazon}
		PTR	`server-18-165-83-110.iad55.r.cloudfront.net`
A	18.165.83.115^{🇺🇸 Amazon}
		PTR	`server-18-165-83-115.iad55.r.cloudfront.net`
A	18.165.83.123^{🇺🇸 Amazon}
		PTR	`server-18-165-83-123.iad55.r.cloudfront.net`

`to`

	NS	`ns01.trs-dns.com`
	NS	`ns10.trs-dns.info`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.org`

Starts with same word
`saml.com`
`saml.ru`
`saml.de`
`saml.pro`
`saml.pl`
`saml.co.uk`
`saml.io`
`saml.to`
`saml.it`
`saml.info`
`saml.fr`
`saml.dk`
`saml.net`
`saml.us`
`saml.ca`
`saml.codes`

Starts similarily
`slam.net.ru`
`lams.ac`
`lmsa.in`
`smla.cl`
`amsl.ca`
`msal.ru`
`asml.org.pk`
`lmsa.adv.br`
`lmas.ca`
`smal.pro`
`masl.in`
`alms.dk`
`slam.ly`
`masl.ru`
`slma.cn`
`masl.to`
`saml.ca`
`lmsa.org`
`alsm.ru`
`lsma.fr`
`lsam.de`
`amls.at`
`lmsa.de`
`smla.co.uk`
`slam.academy`
`salm.us`
`salm.se`
`lams.hk`
`mlas.org`
`saml.codes`
`alsm.org`
`lams.at`
`lams.info`
`alms.k12.ar.us`
`alms.myqnapcloud.com`
`lasm.ca`
`mlas.es`
`mlas.com`
`mlas.dk`
`saml.com`
`alms.nl`
`lmas.info`
`msal.me`
`aslm.de`
`asml.ie`
`lsma.com`
`amsl.or.jp`
`alms.com.au`
`slam.ie`
`slam.nl`
`asml.nl`
`mlsa.es`
`asml.careers`
`slam.studio`
`lsam.ru`
`amsl.ie`
`msal.ch`
`alms.de`
`lams.nl`
`lams.co`
`lasm.com`
`smla.jp`
`slma.lk`
`mals.org.au`
`lmsa.net`
`amsl.nl`
`asml.at`
`lasm.org`
`smla.cn`
`alms.at`
`slam.net`
`asml.pl`
`lsam.solutions`
`alsm.dk`
`amls.it`
`aslm.us`
`masl.us`
`smla.us`
`lams.sg`
`msal.gob.ar`
`asml.it`
`alms.net`
`lams.ch`
`amsl.ru`
`slam.be`
`lmas.biz`
`lmas.us`
`slam.zone`
`alsm.in`
`lams.ca`
`alms.se`
`lasm.fr`
`asml.tel`
`slam.at`
`lasm.ch`
`slam.training`
`alms.info`
`lmsa.pt`
`mals.cn`
`smla.biz`

AI analysis

saml.to is associated with the following four IP addresses: 18.165.83.92, 18.165.83.110, 18.165.83.115, and 18.165.83.123.

IP numbers are shared between saml.to and other host names such as kgmil.or.kr, ef37c5j8rgvjisbfukzks1az8f.hop.clickbank.net, d3ooqhflv82j0h.cloudfront.net, mattwooduk.hop.clickbank.net, and 1clickfix.hop.clickbank.net.

Four name servers, ns-269.awsdns-33.com, ns-906.awsdns-49.net, ns-1291.awsdns-33.org, and ns-1913.awsdns-47.co.uk, are delegated to saml.to.

The name servers of saml.to are at least partially shared with other domains such as hififorum.be, indianahsathletics.org, foragesuperbowl.org, a0k1verse.xyz, and d2emotwo0ekv6g.cloudfront.net.

The name servers ns-376.awsdns-47.com, ns-751.awsdns-29.net, ns-1833.awsdns-37.co.uk, ns-874.awsdns-45.net, ns-842.awsdns-41.net, ns-1062.awsdns-04.org, ns-1618.awsdns-10.co.uk, ns-26.awsdns-03.com, and ns-1090.awsdns-08.org are frequently utilized in conjunction.

ns-269.awsdns-33.com, 2600:9000:5301:d00::1, and 205.251.193.13 are associated in DNS.

ns-906.awsdns-49.net, 2600:9000:5303:8a00::1, and 205.251.195.138 are also connected in DNS.

ns-1291.awsdns-33.org, 2600:9000:5305:b00::1, and 205.251.197.11 point to each other in DNS.

ns-1913.awsdns-47.co.uk, 2600:9000:5307:7900::1, and 205.251.199.121 are linked through DNS as well.

Five mail servers, aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com, handle saml.to.

Other domains such as ummodesign.com, galaxymail.in, hethoutenhuis.org, gihsonline.com, and iamsim.me share at least some mail servers with saml.to.

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are frequently utilized in conjunction.

aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com all point to two IP numbers each: 2607:f8b0:4004:c19::1b, 142.251.111.26, 2a00:1450:400b:c02::1b, 172.253.116.27, 2a00:1450:400c:c00::1a, 173.194.76.26, 2a00:1450:4025:402::1a, 142.250.102.26, 2a00:1450:4013:c1c::1b, and 192.178.156.27 respectively.

dbq