Skip to content

Hostname

orderdi.com

Last fetched

orderdi.com resolves to 35.240.162.152, announced in 35.240.160.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in SG. orderdi.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 · orderdi.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/orderdi.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
andreas roy wikan
Contact emails
roy.wikan@gmail.com, 1741be72-ca8a-4ed3-8e44-9d668ade0b2e@identity-protect.org, 4dac2590-6927-4da6-bdc0-6a285c0193b5@identity-protect.org, 4fe3687f-2b7b-4080-8311-6d1c485effe5@identity-protect.org, cf2278d5-6118-49ee-b1cb-d5eda10fc6ee@identity-protect.org, dad7e09b-35b4-4f6f-80cf-19a59207cae7@identity-protect.org, e717fef4-43fd-44cb-8ca1-d21106c0541f@identity-protect.org, owner-5196628@orderdi.com.whoisprivacyservice.org

Subdomains

Subdomain
admin.orderdi.com
api.orderdi.com
apidev.orderdi.com
chat.orderdi.com
chatdev.orderdi.com
frontenddev.orderdi.com
upload.orderdi.com
uploaddev.orderdi.com
whalelo.orderdi.com
whalelobe.orderdi.com
www.orderdi.com

Showing 11 of 11 subdomains (11 per page).

Mail and authentication

Nameservers

  • ns-403.awsdns-50.com
  • ns-678.awsdns-20.net
  • ns-1286.awsdns-32.org
  • ns-1814.awsdns-34.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • rwbv5pitbly5k7n46rjieeng5m77mkyv45h5qet7dw5mx7hl2mtq.mx-verification.google.com

Threat-feed evidence

History

Related pages

Pivot from orderdi.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: "orderdi.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.