figme.com checked at 2025-02-12T03:03:30.553Z 232ms 109/109/109 100% R:11DNS.NINJA - figme.com
Search for IP or hostnames
figme.com
com
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 1 | |
| (lm) | figme.com |
| 40 | |
| (le) | figem.it |
| (le) | iemfg.net |
| (le) | gemfi.eu |
| (le) | figem.ch |
| (le) | gemfi.es |
| (le) | gefim.it |
| (le) | fgime.com |
| (le) | gifme.ge |
| (le) | megfi.com |
| (le) | iemfg.org |
| (le) | gemfi.de |
| (le) | gefim.be |
| (le) | fgiem.com |
| (le) | figem.com |
| (le) | gemfi.com |
| (le) | fiemg.com |
| (le) | gifem.com |
| (le) | gefim.fr |
| (le) | fiemg.org.br |
| (le) | iemfg.com |
| (le) | imgef.com |
| (le) | gifme.at |
| (le) | figem.com.br |
| (le) | iemfg.us |
| (le) | gemfi.net |
| (le) | mefgi.com |
| (le) | fiemg.com.br |
| (le) | figme.com |
| (le) | fimeg.org |
| (le) | gifme.io |
| (le) | gefim.eu |
| (le) | mgefi.com |
| (le) | gefim.net |
| (le) | figem.fr |
| (le) | gifme.de |
| (le) | mgefi.fr |
| (le) | mefig.com |
| (le) | gmefi.com |
| (le) | gifme.com |
| (le) | mefgi.edu.in |
AI analysis
Two name servers, dns1.registrar-servers.com and dns2.registrar-servers.com, have been delegated for figme.com.
Other domains like bizanaly.com, jenerics.net, phpmelbourne.com, harperbaird.com, and dmrdynamics.com, share the same name server setup as figme.com.
The name servers of figme.com are at least partially shared with other domains such as icbws.com, heartapp.com, okmsr.com, forthewater.org, and emilykk.com.
The name servers dns3.registrar-servers.com, dns4.registrar-servers.com, and dns5.registrar-servers.com are frequently combined and utilized together.
dns1.registrar-servers.com and dns2.registrar-servers.com both point to two IP numbers each: 2610:a1:1024::200, 156.154.132.200 for dns1.registrar-servers.com and 2610:a1:1025::200, 156.154.133.200 for dns2.registrar-servers.com.
The handling of figme.com is carried out by six mail servers: aspmx.l.google.com, 5t524hhy432n2k4ktwr3bc3xxn5puzsyldwbkqwjgsxqwz445wea.mx-verification.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, and alt4.aspmx.l.google.com.
Domains such as ns500699.ns500699.ns500699.ns500693.ns500699.ns500699.ns500693.ns500699.ns500693.ns500699.ns500588.ns500693.ns500588.ns500699.ns500693.ns500588.ns500110.dtrkdll.com, ns500731.ns500731.ns500671.ns500731.ns500742.ns500678.ns500291.ns500291.ns500291.ns500153.tenderladiesbz.com, ns500754.ns500742.ns500742.ns500731.ns500688.ns500671.ns500649.ns500688.ns500671.ns500666.tenderladiesbz.com, ns500699.ns500699.ns500734.ns500693.ns500693.ns500734.ns500588.ns500588.ns500588.ns500588.ns500588.ns500632.ns500632.ns500588.ns500578.ns500110.dtrkdll.com, and ns500693.ns500693.ns500699.ns500734.ns500693.ns500734.ns500734.ns500699.ns500699.ns500588.ns500683.ns500693.ns500683.ns500588.ns500588.ns500612.ns500110.dtrkdll.com share some mail servers, at least partially, with figme.com.
aspmx.l.google.com, 2a00:1450:400c:c00::1b, and 74.125.133.27 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.26 are linked.
alt4.aspmx.l.google.com, 2404:6800:4003:c00::1b, and 74.125.200.26 are correlated.
dbq