Skip to content

Hostname

ediig.com

Last fetched

ediig.com resolves to 13.227.192.22, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. ediig.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 · ediig.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ediig.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of ediig.com owner
Contact emails
domain@autoinspekt.com, ar.karthickbabu@mahindra.com, 03bda365-8f55-4f76-ab96-c412dae2c9a2@identity-protect.org, 52367140-8efa-49eb-b64e-2873250ac590@identity-protect.org, 59b4c091-6b00-4195-b9ab-afbca14053d6@identity-protect.org, c9e8ff20-abc8-4463-a592-95d55ad57880@identity-protect.org

Subdomains

Subdomain
admin.ediig.com
adminv2.ediig.com
api.ediig.com
beta.ediig.com
extservices.ediig.com
mail.ediig.com
ms.ediig.com
notification.ediig.com
origin-test.ediig.com
payments.ediig.com
paymentsapi.ediig.com
rewards.ediig.com

Showing 12 of 51. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns-426.awsdns-53.com
  • ns-834.awsdns-40.net
  • ns-1178.awsdns-19.org
  • ns-1885.awsdns-43.co.uk

MX records

  • aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • a: ediig.com
  • mx: ediig.com
  • include: _spf.google.com
  • ip: 69.39.239.91

Threat-feed evidence

History

Related pages

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