memo.to checked at 2025-01-05T02:41:35.474Z 598ms 148/148/148 100% R:21DNSTREE.COM - memo.to
Search for IP or hostnames
memo.to
to
| NS | tonic.to | ||||||
| NS | cd5.tonic.to | ||||||
| NS | cd6.tonic.to | ||||||
| NS | cd7.tonic.to | ||||||
| NS | cd8.tonic.to | ||||||
| NS | frankfurt.tonic.to | ||||||
| NS | helsinki.tonic.to | ||||||
| NS | la.tonic.to | ||||||
| NS | newyork.tonic.to | ||||||
| NS | singapore.tonic.to | ||||||
| NS | sydney.tonic.to | ||||||
AI analysis
memo.to is configured to point to three IP addresses: 23.23.216.181, 23.23.216.189, and 107.21.240.180.
IP numbers are shared between memo.to and other host names such as ec2-23-23-216-181.compute-1.amazonaws.com, medium.org, ec2-107-21-240-180.compute-1.amazonaws.com, mediumusercontent.com, and ec2-23-23-216-189.compute-1.amazonaws.com.
Four name servers, ns-168.awsdns-21.com, ns-634.awsdns-15.net, ns-1469.awsdns-55.org and ns-1876.awsdns-42.co.uk, are delegated to memo.to.
The name servers of memo.to are at least partially shared with other domains such as oponeo.com.tr, d3lvmyr6619gn7.cloudfront.net, d38w84nuu9j2kr.cloudfront.net, bunch-o-taylors.com, and d1b33tcdu2f7un.cloudfront.net.
The name servers ns-2013.awsdns-59.co.uk, ns-1725.awsdns-23.co.uk, ns-1400.awsdns-47.org, ns-377.awsdns-47.com, ns-888.awsdns-47.net, ns-1011.awsdns-62.net, ns-686.awsdns-21.net, ns-1312.awsdns-36.org, ns-1367.awsdns-42.org, and ns-1730.awsdns-24.co.uk are commonly used in conjunction.
Two IP numbers, 2600:9000:5300:a800::1 and 205.251.192.168, are pointed to by ns-168.awsdns-21.com. Similarly, ns-634.awsdns-15.net directs to 2600:9000:5302:7a00::1 and 205.251.194.122. Moreover, ns-1469.awsdns-55.org is associated with 2600:9000:5305:bd00::1 and 205.251.197.189, and ns-1876.awsdns-42.co.uk points to 2600:9000:5307:5400::1 and 205.251.199.84.
The 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 responsible for handling memo.to.
Just like domains such as ns500759.ns500698.ns500698.ns500758.ns500758.ns500735.ns500698.ns500735.ns500736.ns500698.ns500708.ns500698.ns500619.ns500576.ns500576.trackreceptor.com, ns500759.ns500698.ns500698.ns500736.ns500736.ns500736.ns500698.ns500736.ns500735.ns500576.ns500686.ns500652.ns500652.trackreceptor.com, ns500758.ns500758.ns500758.ns500759.ns500735.ns500735.ns500736.ns500698.ns500698.ns500708.ns500576.ns500698.ns500686.ns500619.ns500576.ns500619.trackreceptor.com, ns500758.ns500759.ns500758.ns500758.ns500736.ns500735.ns500735.ns500698.ns500698.ns500736.ns500708.ns500698.ns500708.ns500708.ns500686.ns500619.ns500576.trackreceptor.com, and ns500759.ns500698.ns500759.ns500735.ns500698.ns500698.ns500698.ns500698.ns500698.ns500708.ns500619.ns500686.ns500619.ns500576.trackreceptor.com, memo.to also shares the same mail server setup.
Some mail servers are at least partially shared between memo.to and other domains, such as treeboxsolutions.com.
aspmx.l.google.com, 2a00:1450:400c:c02::1a, and 74.125.71.26 are related.
alt1.aspmx.l.google.com, 2a00:1450:4013:c16::1a, and 142.250.153.26 are connected.
alt2.aspmx.l.google.com, 2a00:1450:4025:c03::1b, and 142.251.9.27 are associated.
alt3.aspmx.l.google.com, 2a00:1450:4010:c1c::1a, and 142.250.150.27 are linked.
alt4.aspmx.l.google.com, 2404:6800:4003:c00::1b, and 74.125.200.26 are correlated.
johedugfp 2025-01-05 dbq