Hostname
obi.sk
Last fetched
obi.sk resolves to 3.162.38.33, announced in 3.162.36.0/22 by AMAZON-02 - Amazon.com, Inc. in FR. obi.sk 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
- 3.162.38.33
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.162.38.46
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.162.38.67
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.162.38.95
3.162.36.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 99.84.152.110
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.128
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.36
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.74
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for obi.sk is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- registrar:webglobe, a.s.
- Registrant organisation
- obi gmbh & co. deutschland kg
- Contact emails
- noc-domains@net.obi.com, sysadminsdl@wolftheiss.com
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
- ns01.cancom-mase.com
- ns04.cancom-mase.de
- ns05.cancom-mase.eu
- ns02.cancom-mase.net
- ns03.cancom-mase.org
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
SPF policy
- ip: 84.17.184.240/28
- include: _spf.google.com
- a: smtp01.net.obi.com
- a: smtp02.net.obi.com
- a: smtp03.net.obi.com
Threat-feed evidence
History
Related pages
Pivot from obi.sk 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: "obi.sk"})-[: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.