abusix.com Open in urlscan Pro
2606:4700:10::6816:d29  Public Scan

Submitted URL: http://www.xarf.org/
Effective URL: https://abusix.com/xarf/
Submission: On November 01 via api from TR — Scanned from DE

Form analysis 0 forms found in the DOM

Text Content

We value your privacy

We use cookies to enhance your browsing experience, serve personalized ads or
content, and analyze our traffic. By clicking "Accept All", you consent to our
use of cookies.

Customize Reject All Accept All
Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions.
You will find detailed information about all cookies under each consent category
below.

The cookies that are categorized as "Necessary" are stored on your browser as
they are essential for enabling the basic functionalities of the site. ... Show
more

NecessaryAlways Active

Necessary cookies are required to enable the basic features of this site, such
as providing secure log-in or adjusting your consent preferences. These cookies
do not store any personally identifiable data.

 * Cookie
   cookieyes-consent
 * Duration
   1 year
 * Description
   CookieYes sets this cookie to remember users' consent preferences so that
   their preferences are respected on their subsequent visits to this site. It
   does not collect or store any personal information of the site visitors.

 * Cookie
   elementor
 * Duration
   never
 * Description
   This cookie is used by the website's WordPress theme. It allows the website
   owner to implement or change the website's content in real-time.

 * Cookie
   intercom-id-*
 * Duration
   8 months 26 days 1 hour
 * Description
   Intercom sets this cookie that allows visitors to see any conversations
   they've had on Intercom websites.

 * Cookie
   intercom-session-*
 * Duration
   7 days
 * Description
   Intercom sets this cookie that allows visitors to see any conversations
   they've had on Intercom websites.

 * Cookie
   intercom-device-id-*
 * Duration
   8 months 26 days 1 hour
 * Description
   Intercom sets this cookie that allows visitors to see any conversations
   they've had on Intercom websites.

Functional


Functional cookies help perform certain functionalities like sharing the content
of the website on social media platforms, collecting feedback, and other
third-party features.

 * Cookie
   __hssrc
 * Duration
   session
 * Description
   This cookie is set by Hubspot whenever it changes the session cookie. The
   __hssrc cookie set to 1 indicates that the user has restarted the browser,
   and if the cookie does not exist, it is assumed to be a new session.

 * Cookie
   UserMatchHistory
 * Duration
   1 month
 * Description
   LinkedIn sets this cookie for LinkedIn Ads ID syncing.

 * Cookie
   bcookie
 * Duration
   1 year
 * Description
   LinkedIn sets this cookie from LinkedIn share buttons and ad tags to
   recognize browser ID.

 * Cookie
   lidc
 * Duration
   1 day
 * Description
   LinkedIn sets the lidc cookie to facilitate data center selection.

 * Cookie
   bscookie
 * Duration
   1 year
 * Description
   LinkedIn sets this cookie to store performed actions on the website.

 * Cookie
   __hssc
 * Duration
   30 minutes
 * Description
   HubSpot sets this cookie to keep track of sessions and to determine if
   HubSpot should increment the session number and timestamps in the __hstc
   cookie.

 * Cookie
   __cf_bm
 * Duration
   30 minutes
 * Description
   This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.

 * Cookie
   intercom-session-w85zcdmp
 * Duration
   7 days
 * Description
   
   Cookie set by Intercom

Analytics


Analytical cookies are used to understand how visitors interact with the
website. These cookies help provide information on metrics such as the number of
visitors, bounce rate, traffic source, etc.

 * Cookie
   _gcl_au
 * Duration
   3 months
 * Description
   Provided by Google Tag Manager to experiment advertisement efficiency of
   websites using their services.

 * Cookie
   _ga
 * Duration
   1 year 1 month 4 days
 * Description
   The _ga cookie, installed by Google Analytics, calculates visitor, session
   and campaign data and also keeps track of site usage for the site's analytics
   report. The cookie stores information anonymously and assigns a randomly
   generated number to recognize unique visitors.

 * Cookie
   _gid
 * Duration
   1 day
 * Description
   Installed by Google Analytics, _gid cookie stores information on how visitors
   use a website, while also creating an analytics report of the website's
   performance. Some of the data that are collected include the number of
   visitors, their source, and the pages they visit anonymously.

 * Cookie
   _hjFirstSeen
 * Duration
   30 minutes
 * Description
   Hotjar sets this cookie to identify a new user’s first session. It stores a
   true/false value, indicating whether it was the first time Hotjar saw this
   user.

 * Cookie
   _hjAbsoluteSessionInProgress
 * Duration
   30 minutes
 * Description
   Hotjar sets this cookie to detect the first pageview session of a user. This
   is a True/False flag set by the cookie.

 * Cookie
   ajs_anonymous_id
 * Duration
   1 year
 * Description
   This cookie is set by Segment to count the number of people who visit a
   certain site by tracking if they have visited before.

 * Cookie
   __hstc
 * Duration
   5 months 27 days
 * Description
   This is the main cookie set by Hubspot, for tracking visitors. It contains
   the domain, initial timestamp (first visit), last timestamp (last visit),
   current timestamp (this visit), and session number (increments for each
   subsequent session).

 * Cookie
   hubspotutk
 * Duration
   5 months 27 days
 * Description
   HubSpot sets this cookie to keep track of the visitors to the website. This
   cookie is passed to HubSpot on form submission and used when deduplicating
   contacts.

 * Cookie
   ajs_user_id
 * Duration
   never
 * Description
   This cookie is set by Segment to help track visitor usage, events, target
   marketing, and also measure application performance and stability.

 * Cookie
   _hjRecordingLastActivity
 * Duration
   never
 * Description
   Hotjar sets this cookie when a user recording starts and when data is sent
   through the WebSocket.

 * Cookie
   analytics_session_id.last_access
 * Duration
   1 year
 * Description
   Description is currently not available.

 * Cookie
   analytics_session_id
 * Duration
   12 hours
 * Description
   
   Provided by Segment Analytics Manager

 * Cookie
   _hjSessionUser_*
 * Duration
   1 year
 * Description
   Hotjar sets this cookie to ensure data from subsequent visits to the same
   site is attributed to the same user ID, which persists in the Hotjar User ID,
   which is unique to that site.

 * Cookie
   _hjSession_*
 * Duration
   30 minutes
 * Description
   Hotjar sets this cookie to ensure data from subsequent visits to the same
   site is attributed to the same user ID, which persists in the Hotjar User ID,
   which is unique to that site.

Performance


Performance cookies are used to understand and analyze the key performance
indexes of the website which helps in delivering a better user experience for
the visitors.

 * Cookie
   _gat
 * Duration
   1 minute
 * Description
   Google Universal Analytics sets this cookie to restrain request rate and thus
   limit data collection on high-traffic sites.

Advertisement


Advertisement cookies are used to provide visitors with customized
advertisements based on the pages you visited previously and to analyze the
effectiveness of the ad campaigns.

 * Cookie
   test_cookie
 * Duration
   15 minutes
 * Description
   The test_cookie is set by doubleclick.net and is used to determine if the
   user's browser supports cookies.

 * Cookie
   IDE
 * Duration
   1 year 24 days
 * Description
   Google DoubleClick IDE cookies are used to store information about how the
   user uses the website to present them with relevant ads and according to the
   user profile.

 * Cookie
   li_sugr
 * Duration
   3 months
 * Description
   LinkedIn sets this cookie to collect user behaviour data to optimise the
   website and make advertisements on the website more relevant.

Others


Other uncategorized cookies are those that are being analyzed and have not been
classified into a category as yet.

 * Cookie
   _hjIncludedInSessionSample_2914399
 * Duration
   2 minutes
 * Description
   No description

 * Cookie
   analytics_session_id.last_access
 * Duration
   1 year
 * Description
   Description is currently not available.

 * Cookie
   _pk_id.6474.f9aa
 * Duration
   1 year 27 days
 * Description
   Description is currently not available.

 * Cookie
   _pk_ses.6474.f9aa
 * Duration
   30 minutes
 * Description
   Description is currently not available.

Reject All Save My Preferences Accept All
 * Documentation
 * Customer Log In

 * Products
   
   
   
   * Abusix Mail Intelligence
     
     
   
   * AbuseHQ
     
     
 * Pricing
   
   

 * Blog
   
   

 * Company
   
   
   
   * About Us
     
     
   
   * Careers
     
     
 * Contact Us
   
   

 * Products
   
   
   
   * Abusix Mail Intelligence
     
     
   
   * AbuseHQ
     
     
 * Pricing
   
   

 * Blog
   
   

 * Company
   
   
   
   * About Us
     
     
   
   * Careers
     
     
 * Contact Us
   
   

XARF


THE NEW FORMAT OF REPORTING NETWORK ABUSE

To stop attacks or take down illegal content, informing the owner or maintainer
of the source is the only way to mitigate issues and therefore is an essential
part of the internet infrastructure.

 

Join Us Watch a Video

TRUSTED BY




WHAT IS XARF?

Initially started as an open, community-driven effort, XARF is now the industry
standard for sharing network abuse reports. Other than ARF, XARF is independent
of the underlying transport medium as it’s just a simple JSON document that can
be used in multiple channels.




WHEN TO USE XARF?

XARF can be used to report different sorts of abuse, e.g.

 * Spam
 * Phishing attacks
 * Hosted malware
 * Illegal content
 * Copyright issues
 * DDOS attacks

See all types



WHAT TO DO NEXT?

First of all, XARF is a legitimate way of reporting abuse.

 1. Validate it against the schema.
 2. Read or parse the report.
 3. Handle the abuse.
 4. Inform the reporter that you took care of the report.

For more information, read the documentation.



 1. Create a report by modifying an example or writing one from scratch.
 2. Use the schema to validate your report.
 3. Lookup the responsible network owner (eg. with our service ContactDB) and
    send them the report.
 4. The network owner will now be informed about the threat within their network
    and hopefully remediates it.

Note:  If you are using XARF for the first time, please take a look at our
GitHub repository to check for examples.





XARF IS A COMMUNITY EFFORT. BE PART OF IT!

HOW CAN I PARTICIPATE IN XARF?

 1. Start using XARF
 2. Join our GitHub community
 3. Propose new threat types
 4. Discuss proposals

Join Us



FAQS

What abuse types can be reported via XARF?

All supported abuse types can be found in the samples directory on GitHub.

What is the difference between ARF and XARF

While ARF is only meant to report spam via email, XARF is independent of the
underlying transport as it’s just a simple JSON document that you can be used in
multiple channels.
XARF is more versatile as you can also build APIs and don’t need to use
email/SMTP as the underlying tech.

How can I integrate XARF into my current abuse management settings?

XARF can already be used to report different abuse events into your own Abuse
Management Platform like your AbuseHQ instance (internal reporting).

In future, Abusix will offer a central reporting service within our Abusix
Portal which will send reports automatically to the correct recipient.

Who can report abuse via XARF?

Everyone, but usually, this will be users who automate the generation and
sending of the report. In future, everyone who experiences abuse should be able
to report abuse through our Abusix Portal, where an XARF report will be
generated and send to the correct recipients.

Can XARF detect abuse?

No, XARF does not detect abuse. You have to detect abuse within your network,
gather evidence, and then use a XARF to package it up and finally send it to the
correct recipient.

Where can I request new report types?

If you want to participate in XARF, you are more than welcome to. You can
request new report types here.


HOW TO MAKE THE MOST OF XARF

With our abuse management platform AbuseHQ, you'll be able to level up your
internal abuse report handling in an automated way. Let's talk to our team, to
see how we can help you ramp it up!

Get a Demo



RESOURCES & INSIGHTS


NOTHING FOUND

It seems we can’t find what you’re looking for. Perhaps trying different filters
or searching can help.

Abusix provides the missing piece in network security allowing quick and
reliable mitigation of network abuse and other cyber threats.

Linkedin Youtube Facebook-f Twitter Github

TOOLS & SERVICES

 * Abuse Contact DB
 * Blackhole MX
 * XARF

RESOURCES

 * FAQs
 * Blog
 * Glossary
 * Case Studies

COMPANY

 * About Us
 * Careers
 * Contact



INDUSTRY ASSOCIATIONS



© 2023 All Rights Reserved.

 * Imprint
   
   

 * Security
   
   

 * Privacy Policy
   
   

 * Terms of Service
   
   

 * Imprint
   
   

 * Security
   
   

 * Privacy Policy
   
   

 * Terms of Service