Skip to content

Hostname

dragon-models.org

Last fetched

dragon-models.org resolves to 45.91.122.93, announced in 45.91.122.0/24 by NETLOGICS-AS - ADES BV in NL. dragon-models.org 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 · dragon-models.orgRouting diversity1.5/10Peering density6.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/dragon-models.org

Resolution chain

IPv6 resolution

IPv6 resolution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Attribution is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

WHOIS identity

Registrar
iana:1647
Registrant organisation
karim el hamami
Contact emails
hamami@apssupply.com, karimelhamami@googlemail.com

Subdomains

Subdomains is temporarily unavailable.

The graph did not answer within the page budget. Refresh in a moment to retry — fresh data is fetched on the next visit.

Mail and authentication

Nameservers

  • ns2.dehostingfirma.com
  • ns1.dehostingfirma.eu
  • 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
  • ns3.dehostingfirma.org

MX records

  • mail.dragon-models.org

SPF policy

  • a: dragon-models.org
  • mx: dragon-models.org
  • ip: 45.91.122.93

Threat-feed evidence

History

Related pages

Pivot from dragon-models.org 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: "dragon-models.org"})-[: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.