yesing.org checked at 2025-01-09T09:56:28.747Z 312ms 124/124/124 100% R:18DNSTREE.COM - yesing.org
Search for IP or hostnames
yesing.org
org
| NS | a0.org.afilias-nst.info | ||||||
| NS | a2.org.afilias-nst.info | ||||||
| NS | c0.org.afilias-nst.info | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 2 | |
| (lm) | yesing.com |
| (lm) | yesing.com.tw |
| 23 | |
| (le) | ginyes.com |
| (le) | sigeny.com |
| (le) | esying.com |
| (le) | sengyi.com |
| (le) | yesing.com |
| (le) | yiseng.cn |
| (le) | ginesy.com |
| (le) | geniys.com |
| (le) | seying.net |
| (le) | yesing.com.tw |
| (le) | esigny.com |
| (le) | yiseng.com.cn |
| (le) | gniyes.com |
| (le) | iesgny.com |
| (le) | enygis.com |
| (le) | inyges.com |
| (le) | ginesy.eu |
| (le) | yesign.com |
| (le) | singye.bt |
| (le) | seying.org |
| (le) | geniys.ru |
| (le) | ginsey.com |
| (le) | seygin.com |
AI analysis
Four name servers, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com, are delegated to yesing.org.
The name server setup of yesing.org is shared with other domains such as iamprem.com, lit-otomegame.com, salonceleste.com, crinolineupholstery.com, and pinatacoffee.com.
The domain yesing.org shares, at least in part, name servers with other domains such as giagantes.com.
ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, and ns-cloud-c4.googledomains.com each point to two IP numbers respectively: 2001:4860:4802:32::6c, 216.239.32.108; 2001:4860:4802:34::6c, 216.239.34.108; 2001:4860:4802:36::6c, 216.239.36.108; 2001:4860:4802:38::6c, 216.239.38.108.
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 yesing.org.
The mail server setup of yesing.org is identical to that of other domains such as ns500765.ns500734.ns500734.ns500734.ns500734.ns500699.ns500693.ns500699.ns500699.ns500588.ns500588.ns500588.ns500693.ns500588.ns500588.ns500588.dtrkdll.com, ns500699.ns500693.ns500699.ns500683.ns500632.ns500612.ns500588.ns500612.ns500612.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com, ns500698.ns500759.ns500758.ns500698.ns500698.ns500736.ns500698.ns500735.ns500735.ns500698.ns500698.ns500619.ns500619.ns500576.ns500619.trackreceptor.com, ns500742.ns500742.ns500671.ns500731.ns500671.ns500742.ns500731.ns500688.ns500704.ns500704.ns500666.ns500666.ns500291.ns500131.lustychickser.com, and ns500699.ns500699.ns500693.ns500693.ns500699.ns500699.ns500699.ns500683.ns500699.ns500588.ns500612.ns500110.dtrkdll.com.
aspmx.l.google.com, 2a00:1450:400c:c0a::1a, and 74.125.71.26 are associated with each other.
alt1.aspmx.l.google.com, 2a00:1450:4013:c16::1a, and 142.250.153.26 are interconnected.
alt2.aspmx.l.google.com, 2a00:1450:4025:c03::1a, and 142.251.9.26 are linked together.
alt3.aspmx.l.google.com, 2a00:1450:4010:c1c::1a, and 142.250.150.27 are correlated.
alt4.aspmx.l.google.com, 2404:6800:4003:c00::1a, and 74.125.200.27 are related to each other.
johedugfp 2025-01-09 dbq