Hostname
decor2m.com
Last fetched
decor2m.com resolves to 91.134.190.172, announced in 91.134.0.0/16 by OVH - OVH SAS in FR. decor2m.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
- 91.134.190.172
91.134.0.0/16 · OVH - OVH SAS · Roubaix, FR
IPv6 resolution
Attribution
ovh
MAIL_RECEIVER, ORIGIN_AS
WHOIS identity
- Registrar
- iana:269
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- decor2m@wanadoo.fr, 14e1cb0833bfb0c2bcf3cfac45e0ae8dd15615630f992b7c07ec2c944c0decec@decor2m.com.whoisproxy.org, 157280cbfa2238aa2f90ad61e36bb3af549b65e5f1b2a129466edfa66ac80865@decor2m.com.whoisproxy.org, 56c5ab078782ca26364828ce4b83e934aeb185fc84b818aa6bd882bb643b11a2@decor2m.com.whoisproxy.org, 727a38444b6fe4cffbf8138daea1caa9fc6d88f7c360eeb5401db6fbfa833704@decor2m.com.whoisproxy.org, 82296e02e6eed920268679e58661ee0d4214f6dbb440eb46307f02dc770cb645@decor2m.com.whoisproxy.org, b062762b591d7ff0bd62b211d7e3e9710afcaebc537b24c255c6a5a91e117d44@decor2m.com.whoisproxy.org, b2a0b73d31064f3adf5e8cd6c7cdc5b26cc3fe5c4faa19cac3f417d5c146a36b@decor2m.com.whoisproxy.org, e1530e6f28d4e4d9c9a809145aa0889135c533621a7274889bf9e9cefa6f914d@decor2m.com.whoisproxy.org, ed5719ab604019b4fa3635240e7e666d1dcbdd8766fbbf4a3a88046553af5a75@decor2m.com.whoisproxy.org, f41c2f72aea3868cc9850efa4ab3e9206431e366681de805b6b7e795f8ba899e@decor2m.com.whoisproxy.org
Subdomains
Mail and authentication
Nameservers
- ns1.monarobase.net
- ns2.monarobase.net
- ns3.monarobase.net
MX records
- decor2m.com
SPF policy
- a: decor2m.com
- mx: decor2m.com
- include: _spf.monarobase.net
- ip: 5.135.134.136
- ip: 91.134.190.172
- ip: 91.134.190.184
Threat-feed evidence
History
Related pages
Pivot from decor2m.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: "decor2m.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.