Hostname
decorm.com
Last fetched
decorm.com resolves to 13.107.213.40, announced in 13.104.0.0/14 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in CA. decorm.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.107.213.40
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.226.40
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Toronto, CA
- 13.107.246.40
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Montreal, CA
- 13.107.253.40
13.104.0.0/14 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Toronto, CA
IPv6 resolution
No AAAA record for decorm.com is recorded in WhisperGraph.
Attribution
Azure
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- deco recovery mgmt
- Contact emails
- 4xvolc4zesyaxkng@private-contact.com, clx5qxfquz51rkxt@private-contact.com, fb81b29o5rlk78ea@private-contact.com, fqr3tnofc77qh8yk@private-contact.com, fs5mg6fh3nc@networksolutionsprivateregistration.com, g5h9up8vr5s2bsbb@private-contact.com, id6vvnvcahkkw5ne@private-contact.com, mnyqftftc72xi7xg@private-contact.com, sfrqg9mjtivs9zrs@private-contact.com, sixax1yptrenprpi@private-contact.com, smh24cafjnfc5glw@private-contact.com, tedc@decorm.com
Subdomains
Showing 4 of 4 subdomains (4 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns1-04.azure-dns.com
- ns4-04.azure-dns.info
- ns2-04.azure-dns.net
- ns3-04.azure-dns.org
MX records
- d327526a.ess.barracudanetworks.com
- d327526b.ess.barracudanetworks.com
SPF policy
- include: spf.protection.outlook.com
- include: mailgun.org
Threat-feed evidence
History
Related pages
Pivot from decorm.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: "decorm.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.