Hostname
bikar.com
Last fetched
bikar.com resolves to 1 IPv4 address operated by DTAG Internet service provider operations in DE. WHOIS lists iana:226 as the registrar.
Nutrition Label
Resolution chain
bikar.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 62.157.137.25 | 62.156.0.0/14 | AS3320 | DTAG Internet service provider operations | DE |
WHOIS identity
- Registrar
- iana:226
- Organization
- bikar metalle
- Contact emails
- 9551100@bikar.com
- i3c73j5oty33svkgdukvwcshhogtjyn2udvnkhbynrurg@protectedmx.com
- i5pep36jqas5mgntxx5u7jawzwslqf7aocyovc5yyvomw@protectedmx.com
- iabqnde5sghh7cye3cl6gpjkgwuapaike6xbguzqysthc@protectedmx.com
- icb3j3y2ge7zkosbpq6aa3umowxsm75gd4oyj5nild6te@protectedmx.com
- icmfjynox6ih46yf7sbm3xe7eer4qf3y6dp2gcnqm5qyy@protectedmx.com
- iixrntypl5tfpg6kpkpkzdwuthnhuxega4ub2xyyni6gy@protectedmx.com
- ip7vsccheviygnppvivrgbqrc32invlamlzfm3dai5zo4@protectedmx.com
- iuvuihedx43boo6c7orwilmvr5q274ltjtmsoz5yrsnqe@protectedmx.com
- ivz6dxcmbs533pzw4ehaa7or63tvsgnwbrl6h2zie6l6e@protectedmx.com
- registrar@telekom.de
Subdomains
11 observed subdomains of bikar.com.
Web-graph footprint
Distinct hostnames that link to or from bikar.com in the public web crawl.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for bikar.com.
| Mechanism | Target |
|---|---|
| SPF_A | mx.bikar.com |
| SPF_INCLUDE | spf.nl2go.com |
| SPF_IP | 62.157.137.20 |
| SPF_MX | bikar.com |
Related pages
Pivot deeper into the graph from bikar.com.
- IP · 62.157.137.25
- ASN · AS3320DTAG Internet service provider operations
- Registrar · iana:226
- Country · DE
- Email · 9551100@bikar.com
- TLD · .com
- Browse hostnames · bi…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "bikar.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.