Skip to content

Hostname

drinformatique.com

Last fetched

drinformatique.com resolves to 217.160.0.142, announced in 217.160.0.0/16 by IONOS-AS - IONOS SE in DE. drinformatique.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · drinformatique.comRouting diversity1.5/10Peering density7.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/drinformatique.com

Resolution chain

IPv6 resolution

No AAAA record for drinformatique.com is recorded in WhisperGraph.

Attribution

ionos se

ORIGIN_AS

WHOIS identity

Registrar
iana:83
Registrant organisation
this domain was caught by dropcatch.com
Contact emails
drinformatique.com@promoprivacy.com, support@dropcatch.com, dataprivacyprotected@ionos.de, 648eaf2d9460b8afa5c4dc19634b195b-2450864@contact.gandi.net, d0318589fcd94ce8b64a6208ad35a82f-39151878@contact.gandi.net, info@domain-contact.org

Subdomains

Subdomain
autodiscover.drinformatique.com
www.drinformatique.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns1069.ui-dns.biz
  • ns1051.ui-dns.com
  • ns1074.ui-dns.de
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns1065.ui-dns.org

MX records

  • mx00.ionos.fr
  • mx01.ionos.fr

SPF policy

  • include: _spf-eu.ionos.com

Threat-feed evidence

History

Related pages

Pivot from drinformatique.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "drinformatique.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.