WWW.RTSAK.COM - saml.to

Search for IP or hostnames:

saml.to checked at 2025-09-10T17:46:37.594Z 314ms 153/153/153 100% R:18

`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:c1b::1a ^{🇺🇸 Google}
			PTR	`wv-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google}
			PTR	`yuiadrs-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::1a ^{🇮🇪 Google}
			PTR	`dj-in-f26.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::1b ^{🇳🇱 Google}
			PTR	`rb-in-f27.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::1a ^{🇳🇱 Google}
			PTR	`yugrqog-in-f26.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

The DNS record saml.to resolves to the following 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 like kgmil.or.kr, ef37c5j8rgvjisbfukzks1az8f.hop.clickbank.net, d3ooqhflv82j0h.cloudfront.net, mattwooduk.hop.clickbank.net, and 1clickfix.hop.clickbank.net.

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

The domain saml.to shares its name servers, at least partially, 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 commonly utilized in conjunction.

ns-269.awsdns-33.com, ns-906.awsdns-49.net, ns-1291.awsdns-33.org, and ns-1913.awsdns-47.co.uk point to two IP numbers each: 2600:9000:5301:d00::1 and 205.251.193.13, 2600:9000:5303:8a00::1 and 205.251.195.138, 2600:9000:5305:b00::1 and 205.251.197.11, 2600:9000:5307:7900::1 and 205.251.199.121 respectively.

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, are in charge of handling saml.to.

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

The mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com, and aspmx5.googlemail.com are typically 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 each point to two IP numbers: 2607:f8b0:4004:c1b::1a and 192.178.155.26, 2a00:1450:400b:c02::1a and 172.253.116.27, 2a00:1450:400c:c00::1a and 173.194.76.26, 2a00:1450:4025:402::1b and 142.250.102.26, 2a00:1450:4013:c1c::1a and 192.178.156.27 respectively.

dbq